Securing connections to unsecure internet resources

ABSTRACT

There is provided a method for automatically intercepting two or more data packets transported over a computer network, where the data packets originated from client terminal(s), and each data packet comprising transport layer security protocol message(s). The data packets are automatically analyzed to identify secure connection request(s) to an unsecure domain hosted on web server(s), where the secure connection request(s) was received from one or more of the client terminal(s). A digital security certificate is automatically retrieved for the unsecure domain from a trusted certification authority. The digital security certificate is automatically associated with the unsecure domain, thereby converting the unsecure domain to a secure domain. The digital security certificate is automatically sent to a second client terminal in response to a future secure connection request, thereby facilitating a secure connection between the second client terminal and the secure domain.

RELATED APPLICATION/S

This application claims the benefit of priority under 35 USC §119(e) ofU.S. Provisional Patent Application No. 62/243,334 filed Oct. 19, 2015,the contents of which are incorporated herein by reference in theirentirety.

FIELD OF THE INVENTION

The present invention relates to the field of Internet connectionsecurity.

BACKGROUND

Internet resources made available between web servers and clientterminals using domain names, domains, subdomains, or the like, aredefined by the Internet address the resources are located at. Domainsare described, for example, in Mockapetris, P., “Domain names—conceptsand facilities”, IETF STD 13, RFC 1034 [online], November 1987[retrieved on 2015 Sep. 30], retrieved from the Internet:tools.ietf.org/html/rfc1034, DOI: 10.17487/RFC1034, incorporated hereinby reference in its entirety. In further example, domains are describedin Mockapetris, P., “Domain names—implementation and specification”,IETF STD 13, RFC 1035 [online], November 1987, [retrieved on 2015 Sep.30], retrieved from the Internet: http://tools.ietf.org/html/rfc1035,DOI: 10.17487/RFC1035, incorporated herein by reference in its entirety.The Internet resource and client data transferred between the clientterminal and the web server may be transferred in an unencryptedconnection, such as using a hypertext transfer protocol (HTTP), or on asecure and encrypted connection, such as using HTTP (HTTPS).

Web servers usually provide secure connections to client terminal webbrowsers and/or applications using transport layer security (TSL)protocols, secure socket layer (SSL) protocols, and/or the like. The TSLprotocol is described, for example, in Dierks et al., “The TransportLayer Security (TLS) Protocol Version 1.2”, IETF RFC 5246, [online],August 2008 [retrieved on 2015 Sep. 30], retrieved from the Internet:tools.ietf.org/html/rfc6101, DOI: 10.17487/RFC5246, incorporated hereinby reference in its entirety. Such secure connections may use a secureInternet address port 443, a digital certificate, and/or the like. Whenthe client terminal application requires a secure connection, aclienthello security message is sent encapsulated inside a data packetof the computer network infrastructure. The web server may receivesecure connection requests to multiple virtual and/or real web sitesmanaged by the server. The clienthello message may include a Server NameIndication (SNI) field to allow the web server to determine the hostnameand respective digital certificate to send to the client terminalthereby enabling the secure connection. The SNI protocol extension isdescribed, for example, in Blake-Wilson et al., “Transport LayerSecurity (TLS) Extensions”, IETF RFC 3546 [online], June 2003 [retrievedon 2015 Sep. 30], retrieved from the Internet:tools.ietf.org/html/rfc3546, DOI 10.17487/RFC3546, incorporated hereinby reference in its entirety.

A digital certificate (DC) may be issued by a certification authority(CA), such as Comodo, Symantec, GoDaddy, GlobalSign, DigiCert, and thelike. Certificate and certification standards are described, forexample, in Cooper et al., “Internet X.509 Public Key InfrastructureCertificate and Certificate Revocation List (CRL) Profile”, IETF RFC5280 [online], May 2008, [retrieved on 2015 Sep. 30], retrieved from theInternet: tools.ietf.org/html/rfc5280, DOI: 10.17487/RFC5280,incorporated herein by reference in its entirety. The digitalcertificate includes a public key, the identity of the owner, and thelike. The client terminal can then validate the identity of the CA andthereby the validity of the public key before facilitating the secureconnection with the web server. Thus the privacy and integrity of thedata exchanged between the client terminal and the web server isensured.

Data encapsulation layers of an Internet protocol include a link layerfor physical transport of data packets, an Internet layer for directingthe packets to the web servers, a transport layer that may includesecurity protocols, and an application layer that transfers the databetween the cline terminal and the web server applications, such as ahypertext transfer protocol (HTTP) and the like. HTTP standards aredescribed, for example, in Fielding et al., “Hypertext TransferProtocol—HTTP/1.1”, IETF RFC 2616 [online], June 1999, [retrieved on2015 Sep. 30], retrieved from the Internet: tools.ietf.org/html/rfc2616,DOI: 10.17487/RFC2616, incorporated herein by reference in its entirety.When an application or user of a client terminal requires a secureconnection, a special request is made to provide security of thetransport layer to application layer, such as using a HTTP Secure(HTTPS) protocol. An application running on the client terminal mayrequire a secure connection to a web server and an HTTPS protocolcommand is sent to the web server, such asHTTPS://secureconnection.webserver.com/secure_commenction.html and thelike. Such as protocol command initiates a clienthello messageencapsulated in the data packet to facilitate a secure connection to theweb server before transferring date between the client terminal and theweb server. The clienthello message may contain the SNI field to allowthe web server to return the correct DC for the hostnamesecureconnection.webserver.com.

The foregoing examples of the related art and limitations relatedtherewith are intended to be illustrative and not exclusive. Otherlimitations of the related art will become apparent to those of skill inthe art upon a reading of the specification and a study of the figures.

SUMMARY

The following embodiments and aspects thereof are described andillustrated in conjunction with systems, tools, and methods which aremeant to be exemplary and illustrative, not limiting in scope.

There is provided, in accordance to some embodiments, a methodcomprising using one or more hardware processors for performing themethod actions. The method comprises an action of automaticallyintercepting two or more data packets transported over a computernetwork, where the data packets originated from one or more clientterminals, and where the data packets each comprises one or moretransport layer security protocol messages. The method comprises anaction of automatically analyzing the data packets to identify one ormore secure connection requests to an unsecure domain hosted on one ormore web servers, where the secure connection request(s) was receivedfrom one of the client terminal(s). The method comprises an action ofautomatically retrieving a digital security certificate for the unsecuredomain from a trusted certification authority. The method comprises anaction of automatically associating the digital security certificatewith the unsecure domain, thereby converting the unsecure domain to asecure domain. The method comprises an action of automatically sendingthe digital security certificate to a second client terminal in responseto a future secure connection request, thereby facilitating a secureconnection between the second client terminal and the secure domain.

In some embodiments, the analyzing is performed by identifying, in someof the data packets, data packets corresponding to a clienthello-typemessage of a transport layer security protocol, and for each identifiedclienthello-type message, locating a domain name indication, where themethod further comprises statistically analyzing the domain nameindications to determine that the secure connection request is alegitimate client request for a secure connection to the unsecuredomain.

In some embodiments, the method further comprises an action ofdetermining the legitimate request by counting a number of unique clientterminals requesting the secure connection to the unsecure domain, whereeach the unique client terminal is determined to be associated with alegitimate client from parameters of the identified clienthello-typemessage.

In some embodiments, the number of unique client terminals is above apredefined threshold.

In some embodiments, the second client terminal is one of the clientterminal(s).

In some embodiments, the associating comprises hosting the unsecuredomain on a virtual web host.

In some embodiments, the method further comprises an action ofcomparing, based on a certificate rule, the unsecure domain with a listof domains that are each associated with a client rule function, wherethe client rule function is a function of two or more client terminalparameters associated with the client terminal(s).

In some embodiments, the client terminal parameters are analyzed fromsome of the data packets.

In some embodiments, the method further comprises an action of searchingfor some of the client terminal parameters within Internet resourcesassociated with some data from some of the data packets.

In some embodiments, the analyzing uses a blacklist of two or more wordsassociated with illegitimate requests for secure connections.

In some embodiments, the method further comprises a restart operation tothe hardware processor(s) following the associating.

There is provided, in accordance to some embodiments, a computer programproduct comprising a computer readable non-transitory storage medium.The storage medium has encoded thereon a computer code for instructingone or more hardware processors to automatically intercept two or moredata packets transported over a computer network, where the data packetsoriginated from one or more client terminals, and where the data packetseach comprises one or more transport layer security protocol messages.The computer code for instructs the hardware processor(s) toautomatically analyze the data packets to identify one or more secureconnection requests to an unsecure domain hosted on one or more webservers, where the secure connection(s) request was received from one ofthe client terminal(s). The computer code instructs the hardwareprocessor(s) to automatically retrieve a digital security certificatefor the unsecure domain from a trusted certification authority. Thecomputer code instructs the hardware processor(s) to automaticallyassociate the digital security certificate with the unsecure domain,thereby converting the unsecure domain to a secure domain. The computercode instructs the hardware processor(s) to automatically send thedigital security certificate to one or more second client terminals inresponse to one or more future secure connection requests, therebyfacilitating a secure connection between the second client terminal(s)and the secure domain.

In some embodiments, the analyzing is performed by identifying, in someof the data packets, data packets corresponding to a clienthello-typemessage of a transport layer security protocol, and for each identifiedclienthello-type message, locating a domain name indication, where theanalyzing further comprises statistically analyzing the domain nameindications to determine that the secure connection request is alegitimate client request for a secure connection to the unsecuredomain.

In some embodiments, the computer code instructs the hardwareprocessor(s) to determine the legitimate request by counting a number ofunique client terminals requesting the secure connection to the unsecuredomain, where each the unique client terminal is determined to beassociated with a legitimate client from parameters of the identifiedclienthello-type message.

In some embodiments, the number of unique client terminals is above apredefined threshold.

In some embodiments, the second client terminal is one of the clientterminal(s).

In some embodiments, the associating comprises hosting the unsecuredomain on a virtual web host.

In some embodiments, the computer code further compares, based on acertificate rule, the unsecure domain with a list of domains that areeach associated with a client rule function, where the client rulefunction is a function of two or more client terminal parametersassociated with the client terminal(s).

In some embodiments, the client terminal parameters are analyzed fromsome of the data packets.

In some embodiments, the computer code further comprises searching forsome of the client terminal parameters within Internet resourcesassociated with some data from some of the data packets.

There is provided, in accordance to some embodiments, a computerizedsystem comprising a network interface controller and a non-transientcomputer-readable storage medium. The medium has stored thereonprocessor instructions for automatically intercepting two or more datapackets transported via the network interface controller, where the datapackets originated from one or more client terminals, and where the datapackets each comprises one or more transport layer security protocolmessages. The medium has stored thereon processor instructions forautomatically analyzing the data packets to identify one or more secureconnection requests to an unsecure domain hosted, where the secureconnection request(s) was received from one of the client terminal(s).The medium has stored thereon processor instructions for automaticallyretrieving the digital certificate for the unsecure domain from atrusted certification authority. The medium has stored thereon processorinstructions for automatically associating the digital certificate withthe unsecure domain, thereby converting the unsecure domain to a securedomain. The medium has stored thereon processor instructions forautomatically sending the digital certificate to one or more secondclient terminals in response to one or more future secure connectionrequests, thereby facilitating a secure connection between the secondclient terminal(s) and the secure domain. The computerized systemcomprises one or more hardware processors configured to execute theprocessor instructions.

In some embodiments, the analyzing is performed by identifying, in someof the data packets, data packets corresponding to a clienthello-typemessage of a transport layer security protocol, and for each identifiedclienthello-type message, locating a domain name indication, where themethod further comprises statistically analyzing the domain nameindications to determine that the secure connection request is alegitimate client request for a secure connection to the unsecuredomain.

In some embodiments, the medium has stored thereon processorinstructions for determining the legitimate request by counting a numberof unique client terminals requesting the secure connection to theunsecure domain, where each the unique client terminal is determined tobe associated with a legitimate client from parameters of the identifiedclienthello-type message.

In some embodiments, the number of unique client terminals is above apredefined threshold.

In some embodiments, the second client terminal is one of the clientterminal(s).

In some embodiments, the associating comprises hosting the unsecuredomain on a virtual web host.

In some embodiments, the medium has stored thereon processorinstructions for comparing, based on a certificate rule, the unsecuredomain with a list of domains that are each associated with a clientrule function, where the client rule function is a function of two ormore client terminal parameters associated with the client terminal(s).

In some embodiments, the client terminal parameters are analyzed fromsome of the data packets.

In some embodiments, the medium has stored thereon processorinstructions for searching for some of the client terminal parameterswithin Internet resources associated with some data from some of thedata packets.

In addition to the exemplary aspects and embodiments described above,further aspects and embodiments will become apparent by reference to thefigures and by study of the following detailed description.

BRIEF DESCRIPTION OF THE FIGURES

Exemplary embodiments are illustrated in referenced figures. Dimensionsof components and features shown in the figures are generally chosen forconvenience and clarity of presentation and are not necessarily shown toscale. The figures are listed below.

FIG. 1 shows a schematic illustration of a system for automaticallysecuring unsecure domains, according to embodiments of the invention;

FIG. 2A shows a flowchart of an automatic method for securing unsecuredomains, according to embodiments of the invention;

FIG. 2B shows a flowchart of an automatic method for determiningunsecure domain names, according to embodiments of the invention;

FIG. 2C shows a flowchart of an automatic method for obtaining digitalcertificates for unsecure domains, according to embodiments of theinvention; and

FIG. 2D shows a flowchart of an automatic method for convertingtemporary digital certificates to permanent digital certificates,according to embodiments of the invention.

DETAILED DESCRIPTION

According to embodiments of the present invention, there are providedmethods, devices, and systems to facilitate secure connections betweenclient terminals and unsecure web domains. Methods may comprise actionsof automatically intercepting data packets sent to a web server toidentify client terminal requests for secure data connections, such ashypertext transfer protocol secure (HTTPS) connection requests, tounsecure Internet resources, such as web domains. The data packets areanalyzed to identify the Internet resource requested and the clientterminal(s) that are requesting the connection. When the Internetresource and client terminal(s) meet a rule that defines allowableaccess and/or allowable client terminal(s), a public key certificate,such as a digital certificate, is acquired for the secure connection tobe initiated the next time a client terminal requests access to theInternet resource.

Using one or more hardware processors, the web server hosting theunsecure domain may automatically determine that the request for asecure connection was initiated by a legitimate end user of the clientterminal. Unsecure domains are, for example, domains that do not haveassociated digital certificates. The secure connection request is, forexample a clienthello message as defined by the transport layer security(TLS) protocol, is automatically identified in a data packet, and aserver name identification is automatically located, for example in theclienthello message using the Server Name Identification (SNI) field. Byautomatically analyzing the data packet information, the Internetprotocol address (IP) of the client terminal may be determined. When arule regarding the acquisition of a digital certificate (DC) for theunsecure domain is satisfied, the hardware processor automaticallyacquires the DC, and automatically associates the DC with the unsecuredomain for sent in response to new client terminal requests for a secureconnection. This allows automatically converting the unsecure domaininto a secure domain when a legitimate client attempts to access thedomain.

Embodiments of the present invention may allow preventing secureconnection requests from web crawlers, such as web bots, automatedprocesses, and the like, that are not the intended legitimate clients ofthe Internet resource and/or domain. Embodiments of the presentinvention may allow automatically identifying unsecure domains thatclient terminals are trying to access using a secure connection, andconvert the unsecure domains to secure domains being thereby allowingsecure connection access to web domains that were not previouslyaccessible.

Optionally, a blacklist of words is maintained to prevent the web serverfrom facilitating a secure connection to the web domain and/or Internetresource from clients that are not legitimate end users or approved bythe owner of the resource. For example, if a secure connection isrequested from a client terminal that has the word Google, Crawler, andthe like associated with the IP address of the client terminal, thesecure connection request is determined to be associated with a webcrawler and not a legitimate end user.

Optionally, secure connection requests are concentrated on one or moresubdomains of a web domain, and a DC is retrieved for each relevant oneor more subdomain.

Optionally, a web server restart is initiated after a predefined numberof new DCs has been associated with Internet resources on the webserver, thereby updating the corresponding DNS entries. Optionally, whentwo or more hardware processors and/or subsystems exist for a web serversystem, the two or more hardware processors and/or subsystems arerestarted on a rolling basis to prevent a loss of service condition.

Reference is now made to FIG. 1, which is a schematic illustration of asystem 200 for automatically securing unsecure domains 203, according toembodiments of the invention. A web server system 200 may comprise oneor more hardware processors 205, such as in a web server farm, a seriesof rack servers, two or more cores in a single hardware processor, twoor more processors in a single blade server, and the like, which areexamples of multiple processors for managing web resources. FIG. 1 andother drawings describe a simple example embodiment, where the webresource hosting environment is also a computerized system carrying outthe embodiment, but in other embodiments, actions may be distributeddifferently between one or more hardware processors in a virtualized webresource environment, a system of systems, and the like. System 200comprises a network interface 206 for communicating with a certificateauthority 210 and one or more client terminals 221. For example,certificate authority 210 receives an application programming interface(API) communication from hardware processor 205 requesting a digitalcertificate 207E for a domain 203 through network interface 206. Thehardware processor(s) 205 may receive HTTP(S) 220 protocol data packetsfrom client terminal(s) 221 through network interface 206. Networkinterface 206 may comprise a specific port 206A, such as port 80, fornon-secure protocol data packets 220A, and a specific port 206B, such asport 443, for secure data packets 220B.

Web server system 200 may comprise a local or networked repository 207,such as a non-transient computer-readable storage medium, a hard disk, anetwork attached storage, and the like, for storing a program code.Specifically, a program store may store program code for an automaticdata packet interceptor and analyzer 207A that comprises program code toinstruct hardware processor(s) 205 to intercept HTTP(S) data packets 220and determine the domain name of a domain 203 and/or subdomain name of asubdomain 204 stored on repository 207. Data packet interceptor andanalyzer 207A may also determine one or more parameters 221P of clientterminal(s) 221, such as IP address, physical location, ownership, username, client terminal type, and/or the like, and store client terminalparameters 221P in a client terminal database (DB) 207D. For example, aclient terminal type may be a virtual terminal operated by a webcrawler, and the owner name may be Google™, such as a web crawler andthe like. A rule manager 207C may comprise program code to instructhardware processor(s) 205 to retrieve a digital certificate 207E fromanalysis of domain names and client terminal parameters 221P. Anautomatic certificate manager 207B may comprise program code to instructhardware processor(s) 205 to retrieve a digital certification (DC) 207Efrom certificate authority 210, and may store DC 207E on repository 207.The program code for performing the actions described herein may bearranged in modules as described or in other modules according torequirements.

Reference is now made to FIG. 2A, which is a flowchart of an automaticmethod 100 for securing unsecure domains, according to embodiments ofthe invention. Method 100 comprises an automatic action of intercepting101 data packets, such as by copying data packets from hardware port 443as at 206B of FIG. 1, for example by inserting an operating systemservice to instruct hardware processor(s) 205 to intercept data packets.Method 100 comprises an automatic action of analyzing 102 the datapackets to determine a name of a domain 203 and/or subdomain 204, clientterminal parameters 221P, and the like. Optionally, client terminalparameters 221P are stored in a client terminal database 207D. Whenclient terminal parameters 221P comply with a rule 103 for domain 203and/or subdomain 204, a digital certificate 207E is automaticallyretrieved 104 and automatically associated 105 with corresponding domain203 and/or subdomain 204 on web server system 205. Program code storedin a rule manager 207C may instruct hardware processor(s) 205 todetermine when a rule and/or condition is met 103, such as when a clientterminal from a target neighborhood has accessed the web domain. When anew client terminal requests a secure connection for domain 203 and/orsubdomain 204, a corresponding digital certificate 207E is sent 106during the TLS protocol negotiation between the new client terminal andweb server 200.

Reference is now made to FIG. 2B, which is a flowchart of an automaticmethod 110 for determining unsecure domain names, according toembodiments of the invention. When a data packet is received 111 vianetwork interface 206 of FIG. 1, hardware processor(s) 205 identifieswhen the data packet contains a request for a secure connection, such asa clienthello message 112. Program code stored in a data packetinterceptor and analyzer 207A may instruct hardware processor(s) 205 todetermine when 112 a data packet 220 contains a clienthello message.When the data packet contains the clienthello message, hardwareprocessor(s) 205 determine if the message also contains a domain and/orsubdomain identifier, such as a server name identifier 113. When bothconditions 112 and 113 exist, a domain name is extracted 114 from thedata packet. Optionally, client terminal parameters 221P are determined115 from a data packet, such as a client terminal Internet protocoladdress, MAC address, geographical location, user name, and the like.Optionally, secondary parameters are determined 115 by searching fordata packet parameters, such as using a search engine, an informationservice, a database, and the like. The domain name and client terminalparameters 221P may be stored 116 in a client DB for further use.

Reference is now made to FIG. 2C, which is a flowchart of an automaticmethod 120 for obtaining digital certificates for unsecure domains,according to embodiments of the invention. When data in received datapackets has complied with a rule, a digital certificate information isdetermined 121, such as domain name, domain owner, and the like. The DCinformation is submitted automatically 122 on a certificate signingrequest, such as using an API interface to certificate authority (CA)210. Web server system 200 receives 123 from CA 210 a DC identification(ID) code. A virtual hosting setup, such as a virtual web host, may becreated 125 for domain 203 and/or subdomain 204, and the DC ID code isplaced 124 on the domain, such as in a hypertext markup languagedocument, a web document, a text document, and/or the like. Hardwareprocessor(s) 205 may send a request to modify 126 the domain name serverentry for the domain if needed. When the domain is verified by CA 127,the DC is retrieved 129 from CA 210, and associated 130 with the domainname on web server system 200.

Reference is now made to FIG. 2D, which is a flowchart of an automaticmethod 140 for converting temporary digital certificates to permanentdigital certificates, according to embodiments of the invention.Optionally, a temporary DC is retrieved 141 and associated with thedomain name prior to retrieving 144 a permanent DC. For example, a webserver 200 monitors 142 a secure connection until a permanent DC rule issatisifed 143 and then the permanent DC is retrieved. When a number ofunique client terminals exceeds a predefined threshold determined by apermanent DC rule, a permanent DC may be retrieved 144.

In some embodiments of the invention, public key encryption is used toestablish secure data connections between a client terminal and anInternet Resource hosted on a web server. The resource owner iscontacted to approve the secure connection for the client terminal, andthe owner allows a temporary or permanent public key certificate forencryption of the secure data connection. The certificate includesinformation on the key, the owner and a digital signature verifying thecontents of the certificate. The certificate allows the owner to controlthe access of client terminals to the Internet resource, for example bydigital certificates provided by a certificate authority and describedherein as TLS and/or SSL security.

When a web server receives a secure connection request to an unsecureInternet resource, such as a web domain without a DC, the connection isrejected and the request is ignored by the server. The unsuccessfulsecure connection requests may not be logged by the server. Since thereis log on the server of unsuccessful requests, the web server is notcapable of automatically detecting these requests and taking correctiveaction to secure the unsecure Internet resource. Embodiments of thepresent invention allow detecting these requests associating a temporaryor permanent DC with the Internet resource.

Since many new web sites may be experimental, temporary, transitional,and the like, the cost of acquiring a digital certificate (DC) from alarge numbers of new sites may be very high. Furthermore, many webcrawlers, bots, Internet search providers, and the like, are not theintended clients for the web sites but may continuously and frequentlyaccess web sites to acquire information on the web sites for their ownpurposes. An owner of a web site, a web hosting service, and the likemay want to optimize the expenses acquiring DCs for multiple sites bypostponing the acquisition as much as possible, avoid acquiring DCs forobsolete or unused web sites, and the like.

In some secure connection request circumstances, a web server may have avery large list of DCs for an Internet resource, and send a truncatedlist of DCs to the client terminal to avoid overloading the networkconnection bandwidth. In these cases, some embodiments of the inventionmay determine the correct DC to send the client based on information inthe client terminal database.

In the description and claims of the application, each of the words“comprise” “include” and “have”, and forms thereof, are not necessarilylimited to members in a list with which the words may be associated. Inaddition, where there are inconsistencies between this application andany document incorporated by reference, it is hereby intended that thepresent application controls.

What is claimed is:
 1. A method comprising using at least one hardwareprocessor for: automatically intercepting a plurality of data packetstransported over a computer network, wherein said plurality of datapackets originated from at least one client terminal, and wherein saidplurality of data packets each comprises at least one transport layersecurity protocol message; automatically analyzing said plurality ofdata packets to identify at least one secure connection request to anunsecure domain hosted on at least one web server, wherein said at leastone secure connection request was received from at least one of said atleast one client terminal; automatically retrieving a digital securitycertificate for said unsecure domain from a trusted certificationauthority; automatically associating said digital security certificatewith said unsecure domain, thereby converting said unsecure domain to asecure domain; automatically sending said digital security certificateto a second client terminal in response to a future secure connectionrequest, thereby facilitating a secure connection between said secondclient terminal and said secure domain.
 2. The method of claim 1,wherein said analyzing is performed by: identifying, in some of saidplurality of data packets, data packets corresponding to aclienthello-type message of a transport layer security protocol; and foreach identified clienthello-type message, locating a domain nameindication, wherein the method further comprises statistically analyzingsaid domain name indications to determine that said secure connectionrequest is a legitimate client request for a secure connection to saidunsecure domain.
 3. The method of claim 2, further comprising an actionof determining said legitimate request by counting a number of uniqueclient terminals requesting said secure connection to said unsecuredomain, wherein each said unique client terminal is determined to beassociated with a legitimate client from parameters of said identifiedclienthello-type message.
 4. The method of claim 3, wherein said numberof unique client terminals is above a predefined threshold.
 5. Themethod of claim 1, wherein said associating comprises hosting saidunsecure domain on a virtual web host.
 6. The method of claim 1, furthercomprising an action of comparing, based on a certificate rule, saidunsecure domain with a list of domains that are each associated with aclient rule function, wherein said client rule function is a function ofa plurality of client terminal parameters associated with said at leastone client terminal.
 7. The method of claim 6, wherein said plurality ofclient terminal parameters are analyzed from some of said plurality ofdata packets.
 8. The method of claim 6, further comprising an action ofsearching for some of said plurality of client terminal parameterswithin Internet resources associated with some data from some of saidplurality of data packets.
 9. The method of claim 1, wherein saidanalyzing uses a blacklist of a plurality of words associated withillegitimate requests for secure connections.
 10. A computer programproduct comprising a computer readable non-transitory storage medium,said storage medium having encoded thereon a computer code forinstructing at least one hardware processor to: automatically intercepta plurality of data packets transported over a computer network, whereinsaid plurality of data packets originated from at least one clientterminal, and wherein said plurality of data packets each comprises atleast one transport layer security protocol message; automaticallyanalyze said plurality of data packets to identify at least one secureconnection request to an unsecure domain hosted on at least one webserver, wherein said at least one secure connection request was receivedfrom at least one of said at least one client terminal; automaticallyretrieve a digital security certificate for said unsecure domain from atrusted certification authority; automatically associate said digitalsecurity certificate with said unsecure domain, thereby converting saidunsecure domain to a secure domain; automatically send said digitalsecurity certificate to at least one second client terminal in responseto at least one future secure connection requests, thereby facilitatinga secure connection between said at least one second client terminal andsaid secure domain.
 11. The computer program product of claim 10,wherein said analyzing is performed by: identifying, in some of saidplurality of data packets, data packets corresponding to aclienthello-type message of a transport layer security protocol; and foreach identified clienthello-type message, locating a domain nameindication, wherein the analyzing further comprises statisticallyanalyzing said domain name indications to determine that said secureconnection request is a legitimate client request for a secureconnection to said unsecure domain.
 12. The computer program product ofclaim 11, further comprising determining said legitimate request bycounting a number of unique client terminals requesting said secureconnection to said unsecure domain, wherein each said unique clientterminal is determined to be associated with a legitimate client fromparameters of said identified clienthello-type message.
 13. The computerprogram product of claim 10, wherein said associating comprises hostingsaid unsecure domain on a virtual web host.
 14. The computer programproduct of claim 10, further comprises comparing, based on a certificaterule, said unsecure domain with a list of domains that are eachassociated with a client rule function, wherein said client rulefunction is a function of a plurality of client terminal parametersassociated with said at least one client terminal.
 15. The computerprogram product of claim 14, wherein said plurality of client terminalparameters are analyzed from some of said plurality of data packets. 16.The computer program product of claim 14, further comprising searchingfor some of said plurality of client terminal parameters within Internetresources associated with some data from some of said plurality of datapackets.
 17. A computerized system, comprising: a network interfacecontroller; a non-transient computer-readable storage medium havingstored thereon processor instructions for: automatically intercepting aplurality of data packets transported via said network interfacecontroller, wherein said plurality of data packets originated from atleast one client terminal, and wherein said plurality of data packetseach comprises at least one transport layer security protocol message,automatically analyzing said plurality of data packets to identify atleast one secure connection request to an unsecure domain hosted,wherein said at least one secure connection request was received from atleast one of said at least one client terminal, automatically retrievingsaid digital certificate for said unsecure domain from a trustedcertification authority, automatically associating said digitalcertificate with said unsecure domain, thereby converting said unsecuredomain to a secure domain, and automatically sending said digitalcertificate to at least one second client terminal in response to atleast one future secure connection requests, thereby facilitating asecure connection between said at least one second client terminal andsaid secure domain; at least one hardware processor configured toexecute said processor instructions.
 18. The computerized system ofclaim 17, wherein said analyzing is performed by: identifying, in someof said plurality of data packets, data packets corresponding to aclienthello-type message of a transport layer security protocol; and foreach identified clienthello-type message, locating a domain nameindication, wherein the analyzing further comprises statisticallyanalyzing said domain name indications to determine that said secureconnection request is a legitimate client request for a secureconnection to said unsecure domain.
 19. The computerized system of claim18, further determining said legitimate request by counting a number ofunique client terminals requesting said secure connection to saidunsecure domain, wherein each said unique client terminal is determinedto be associated with a legitimate client from parameters of saididentified clienthello-type message.
 20. The computerized system ofclaim 17, further comprising comparing, based on a certificate rule,said unsecure domain with a list of domains that are each associatedwith a client rule function, wherein said client rule function is afunction of a plurality of client terminal parameters associated withsaid at least one client terminal.